Apparatus, system and method of controlling data flow to a plurality of endpoints over a communication network

ABSTRACT

Some demonstrative embodiments include apparatuses, systems and/or methods of controlling data flow over a communication network. For example, an apparatus may include a communication unit to control the transfer of a stream of data from a first device to a second device over a communication link, the stream of data including data to be delivered to a plurality of endpoints. For example, the controlling may include communicating between the first and second devices at least one message including at least one endpoint-specific credit consumption unit (CCU) defined with respect to at least one endpoint of the plurality of endpoints.

CROSS REFERENCE

This application claims the benefit of and priority from U.S.Provisional Patent application No. 61/729,368 entitled “Apparatus,System, and Method of Controlling Data Flow Over a WirelessCommunication Link”, filed Nov. 22, 2012, the entire disclosure of whichis incorporated herein by reference.

TECHNICAL FIELD

Embodiments described herein generally relate to controlling data flowover a communication network.

BACKGROUND

Some wireless communication technologies may be configured forcommunication of various dedicated services.

For example, the Wireless-Gigabit (WiGig) technology, e.g., according tothe Wireless Gigabit Alliance, Inc WiGig MAC and PHY SpecificationVersion 1.1, April 2011, Final specification, is designed to carrymultiple dedicated services, such as audio-visual (A/V) and input output(I/O).

The WiGig Alliance (WGA) has defined a set of Protocol AbstractionLayers (PALs), e.g., a WiGig Serial Extension (WSE) PAL and a WiGigDisplay Extension (WDE) PAL, that standardize the method of transportingtraffic of specific industry-standard protocols, e.g. Universal SerialBus (USB) and DisplayPort, over the WiGig media access control (MAC)layer.

The WSE defines a WSE host communicating with a WSE device over a WiGigwireless link interface. The WSE host can connect and control severalWSE devices. Each WSE device can include several USB ports, and each USBport can be attached to a USB device or be extended to several ports viaa USB hub.

Since USB devices and/or USB hosts may be configured for communicatingover a physical medium, e.g., a USB cable, there may be a problem toperform some operations, e.g., in an efficient seamless and/ortransparent manner, via the WSE PAL.

The WSE device typically includes a buffer for buffering data receivedfrom the WSE host to be delivered to USB devices integrated within orconnected to the WSE device. The size of the buffer may affectthroughput and/or latency of the data flow between the host and the USBdevices.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system, inaccordance with some demonstrative embodiments.

FIG. 2 is a schematic illustration of a sequence of communicationsbetween a Wireless-Gigabit (WiGig) Serial Extension (WSE) host, and aWSE device, in accordance with some demonstrative embodiments.

FIG. 3 is a schematic flow-chart illustration of a method of controllingdata flow, in accordance with some demonstrative embodiments.

FIG. 4 is a schematic illustration of a product, in accordance with somedemonstrative embodiments.

DESCRIPTION OF EMBODIMENTS

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality”, as used herein, include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

References to “one embodiment,” “an embodiment,” “demonstrativeembodiment,” “various embodiments,” etc., indicate that theembodiment(s) so described may include a particular feature, structure,or characteristic, but not every embodiment necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one embodiment” does not necessarily refer to the sameembodiment, although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first,” “second,” “third,” etc., to describe a commonobject, merely indicate that different instances of like objects arebeing referred to, and are not intended to imply that the objects sodescribed must be in a given sequence, either temporally, spatially, inranking, or in any other manner.

Some embodiments may be used in conjunction with various devices andsystems, for example, a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, an Ultrabook™ computer, a server computer, a handheldcomputer, a handheld device, a Personal Digital Assistant (PDA) device,a handheld PDA device, an on-board device, an off-board device, a hybriddevice, a vehicular device, a non-vehicular device, a mobile or portabledevice, a consumer device, a non-mobile or non-portable device, awireless communication station, a wireless communication device, awireless Access Point (AP), a wired or wireless router, a wired orwireless modem, a video device, an audio device, an audio-video (A/V)device, a wired or wireless network, a wireless area network, a WirelessVideo Area Network (WVAN), a Local Area Network (LAN), a Wireless LAN(WLAN), a Personal Area Network (PAN), a Wireless PAN (WPAN), and thelike.

Some embodiments may be used in conjunction with devices and/or networksoperating in accordance with existing Wireless-Gigabit-Alliance (WGA orWiGig) specifications (Wireless Gigabit Alliance, Inc WiGig MAC and PHYSpecification Version 1.1, April 2011, Final specification) and/orfuture versions and/or derivatives thereof, devices and/or networksoperating in accordance with existing WiGig Serial Extension (WSE)protocols (WiGig Serial Extension (WSE) Specification Draft 1.02, August2012) and/or future versions and/or derivatives thereof, devices and/ornetworks operating in accordance with existing WiGig Display Extension(WDE) protocols (WDE Draft Specification 1.04, August 2012) and/orfuture versions and/or derivatives thereof, devices and/or networksoperating in accordance with existing WiGig Bus Extension (WBE)protocols (WiGig Bus Extension Spec (WBE), Version 1.0 June 2011) and/orfuture versions and/or derivatives thereof, devices and/or networksoperating in accordance with existing WiGig Secure Digital (SD)Extension (WSD) protocols (WiGig SD Extension (WSD) PAL SpecificationDraft 1.0 August 2012) and/or future versions and/or derivativesthereof, devices and/or networks operating in accordance with existingBulk Only Transfer (BOT) Protocols (Universal Serial Bus (USB) MassStorage Class Bulk-Only Transport, Revision 1.0, Sep. 31, 1999) and/orfuture versions and/or derivatives thereof, devices and/or networksoperating in accordance with existing IEEE 802.11 standards (IEEE802.11-2012, IEEE Standard for Information technology—Telecommunicationsand information exchange between systems Local and metropolitan areanetworks—Specific requirements Part 11: Wireless LAN Medium AccessControl (MAC) and Physical Layer (PHY) Specifications, Mar. 29, 2012;IEEE802.11 task group ac (TGac) (“IEEE802.11-09/0308r12—TGac ChannelModel Addendum Document”); IEEE 802.11 task group ad (TGad) (IEEEP802.11ad/D9.0 Draft Standard for InformationTechnology—Telecommunications and Information Exchange BetweenSystems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment 5: Enhancements for Very High Throughput in the60 GHz Band)), and/or future versions and/or derivatives thereof,devices and/or networks operating in accordance with existing IEEE802.16 standards (IEEE-Std 802.16, 2009 Edition, Air Interface for FixedBroadband Wireless Access Systems; IEEE-Std 802.16e, 2005 Edition,Physical and Medium Access Control Layers for Combined Fixed and MobileOperation in Licensed Bands; amendment to IEEE Std 802.16-2009,developed by Task Group m) and/or future versions and/or derivativesthereof, devices and/or networks operating in accordance with existingWirelessHD™ specifications and/or future versions and/or derivativesthereof, units and/or devices which are part of the above networks, andthe like.

Some embodiments may be used in conjunction with one way and/or two-wayradio communication systems, cellular radio-telephone communicationsystems, a mobile phone, a cellular telephone, a wireless telephone, aPersonal Communication Systems (PCS) device, a PDA device whichincorporates a wireless communication device, a mobile or portableGlobal Positioning System (GPS) device, a device which incorporates aGPS receiver or transceiver or chip, a device which incorporates an RFIDelement or chip, a Multiple Input Multiple Output (MIMO) transceiver ordevice, a Single Input Multiple Output (SIMO) transceiver or device, aMultiple Input Single Output (MISO) transceiver or device, a devicehaving one or more internal antennas and/or external antennas, DigitalVideo Broadcast (DVB) devices or systems, multi-standard radio devicesor systems, a wired or wireless handheld device, e.g., a Smartphone, aWireless Application Protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Infra Red (IR), Frequency-Division Multiplexing (FDM),Orthogonal FDM (OFDM), Time-Division Multiplexing (TDM), Time-DivisionMultiple Access (TDMA), Extended TDMA (E-TDMA), General Packet RadioService (GPRS), extended GPRS, Code-Division Multiple Access (CDMA),Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrierCDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT),Bluetooth®, Global Positioning System (GPS), WiGig, Wi-Fi,Internet-Protocol (IP), Wi-Max, ZigBee™, Ultra-Wideband (UWB), GlobalSystem for Mobile communication (GSM), 3rd Generation PartnershipProject (3GPP), 2G, 2.5G, 3G, 3.5G, Long Term Evolution (LTE), LTEadvanced, Fifth Generation (5G) mobile networks, Enhanced Data rates forGSM Evolution (EDGE), or the like. Other embodiments may be used invarious other devices, systems and/or networks.

The term “wireless device”, as used herein, includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the term “wireless device” may optionallyinclude a wireless service.

The term “communicating” as used herein with respect to a communicationsignal includes transmitting the communication signal and/or receivingthe communication signal. For example, a communication unit, which iscapable of communicating a communication signal, may include atransmitter to transmit the communication signal to at least one othercommunication unit, and/or a communication receiver to receive thecommunication signal from at least one other communication unit.

Some demonstrative embodiments may be used in conjunction with suitablelimited-range or short-range wireless communication networks, forexample, a wireless area network, a “piconet”, a WPAN, a WVAN and thelike. Other embodiments may be used in conjunction with any othersuitable wireless communication network.

Some demonstrative embodiments may be used in conjunction with awireless communication network communicating over a frequency band of 60GHz. However, other embodiments may be implemented utilizing any othersuitable wireless communication frequency bands, for example, anExtremely High Frequency (EHF) band (the millimeter wave (mmwave)frequency band), e.g., a frequency band within the frequency band ofbetween 30 Ghz and 300 GHZ, a WLAN frequency band, a WPAN frequencyband, a WiGig frequency band according to the WGA specification, a WiFiband, a P2P band, and the like.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In someembodiments, the antenna may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, the antenna may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements. The antenna may include, for example, a phased array antenna,a single element antenna, a set of switched beam antennas, and/or thelike.

The term “station” (STA), as used herein, may include any logical entitythat is a singly addressable instance of a medium access control (MAC)and a physical layer (PHY) interface to a wireless medium (WM).

The phrase “access point” (AP), as used herein, may include an entitythat contains one station (STA) and provides access to distributionservices, via the WM for associated STAs.

The term “beamforming”, as used herein, may relate to a spatialfiltering mechanism, which may be used at a transmitter and/or areceiver to improve the received signal power or signal-to-noise ratio(SNR) at an intended receiver.

The phrase “non-access-point (non-AP) station (STA)”, as used herein,may relate to a STA that is not contained within an AP.

The phrases “directional multi-gigabit (DMG)” and “directional band”(DBand), as used herein, may relate to a frequency band wherein theChannel starting frequency is above 40 GHz.

The phrases “DMG STA” and “mmWave STA (mSTA)” may relate to a STA havinga radio transmitter, which is operating on a channel that is within theDMG band.

The phrase “peer to peer (PTP or P2P) communication”, as used herein,may relate to device-to-device communication over a wireless link(“peer-to-peer link”) between a pair of devices. The P2P communicationmay include, for example, wireless communication over a direct linkwithin a QoS basic service set (BSS), a tunneled direct-link setup(TDLS) link, a STA-to-STA communication in an independent basic serviceset (IBSS), or the like.

A wireless P2P wireless communication network (“P2P network” or “P2Pgroup”) may include a plurality of wireless communication devicescapable of supporting device-to device communication.

The phrase “Protocol Adaptation Layer (PAL)”, as used herein, mayinclude an abstraction layer configured to enable transporting trafficof at least one predefined protocol over a communication link. Thepredefined standard may include, for example, a specificindustry-standard protocol, e.g. USB, DisplayPort, and the like. The PALmay be above a data link layer, for example, a MAC layer, and/or above atransport layer, e.g., a Transmission Control Protocol (TCP) or UserDatagram Protocol (UDP), which is above the data link layer. In oneexample, the data link layer may include, for example, a MAC layer of awireless link, e.g., a WiFi MAC layer, a WiGig MAC layer, a P2P MAClayer, and the like. In another example, the PAL may be above atransport layer, e.g., a TCP or UDP, which may be configured fortransporting traffic over an IP network, e.g., a wired or wirelessInternet link and/or Ethernet link.

Some demonstrative embodiment are described herein with respect to a PALconnection over a wireless communication link, for example, a WiGiglink, e.g., as described below. However, other embodiments may include aPAL connection over any other wired or wireless communication MAC layerlink, e.g., an IP link.

The phrase “PAL communication unit”, as used herein, may include acommunication element to manage and/or control a PAL connection betweena first architectural element, for example, a PAL host, e.g., a USBhost, and a second architectural element, for example, a PAL device,e.g., a USB device, over a communication link, e.g., a MAC layer link ora transport layer link, between the PAL communication unit and anotherPAL communication unit.

In some demonstrative embodiments, the PAL communication unit (alsoreferred to as “PAL manager”, “PAL communication controller” or “PALcontroller”) may perform the functionality of, may include, or may beimplemented as part of a WSE Service Set (WSS). For example, the PALcommunication unit may perform at least part of the functionality of aWSE device or a WSE host, e.g., as described below. In otherembodiments, the PAL communication unit may perform the functionality ofany other PAL device, element and/or module.

The phrase “WSE device”, as used herein, may include, for example, a WSEarchitectural element that integrates, and/or is associated with, atleast one device, e.g., a USB device, and manages transfers, e.g., USBtransfers, targeting the integrated device over a network connection. Inone example, the integrated device may be connected, for example,through a wired USB, e.g., USB cable, USB chip-to-chip interconnect,and/any other technologies. In one example, the integrated device may bepresented through the WSE device to a host as a USB device compliantwith a USB specification, e.g., the USB 2.0 and/or USB 3.0Specifications.

In one example, the WSE device may optionally include any computingplatform, e.g., a portable device, which houses and/or performs thefunctionality of the WSE device and, optionally, one or more additionalelements, e.g., drivers and/or application software, configured toperform the functionality of a peripheral device. In other embodiments,the WSE device may include and/or may be implemented by any otherportable or non-portable device.

In some demonstrative embodiments, the WSE device may include USB devicelogic, e.g., for communicating with a USB device according to a USBSpecification, a WSE device PAL, e.g., to control communication over thePAL, and a network interface, e.g., to communicate over thecommunication link. For example, the WSE device PAL may interfacebetween the USB device logic and the network interface, e.g., in atransparent manner. In other embodiments, the WSE device may include anyother elements. In one example, the PAL communication unit may performthe functionality of at least the WSE device PAL, e.g., a device USBPAL.

The phrase “WSE host”, as used herein, may include an architecturalelement of the WSE PAL that includes a communication architecture, e.g.,a WiGig MAC and PHY, and USB host logic, e.g., as defined by a USBSpecification, e.g., the USB 2.0 and/or USB 3.0 Specifications.

In one example, the WSE host may optionally include any computingplatform, e.g., a personal computer, which houses and/or performs thefunctionality of the WSE host and, optionally, one or more additionalelements, e.g., drivers and/or application software, configured toperform the functionality of a host device. In other embodiments, theWSE host may include and/or may be implemented by any other portable ornon-portable device.

In some demonstrative embodiments, the WSE host may include USB hostlogic, e.g., for communicating with a USB host according to a USBSpecification, a WSE host PAL, e.g., to control communication over thePAL, and a network interface, e.g., to communicate over thecommunication link. For example, the WSE host PAL may interface betweenthe USB host logic and the network interface, e.g., in a transparentmanner. In other embodiments, the WSE host may include any otherelements. In one example, the PAL communication unit may perform thefunctionality of at least the WSE host PAL, e.g., a host USB PAL.

An endpoint may include, for example, an architectural element, which isassociated with a first device, which in turn is configured to interfacebetween the endpoint and a second device over a communication link. Forexample, the endpoint may be integrated as part of the first device orconnected to the first device via one or more other devices and/orconnections. The endpoint may be implemented, for example, using anytechnology, e.g., software, hardware and/or any combination thereof. Thefirst device may include and/or interface between one or more endpointsand the second device.

In one example, the first device may include a WSE device and the seconddevice may include a WSE host. For example, the endpoint may belong to aUSB device, e.g., a USB device, which may be integrated into the WSEdevice or connected, e.g., through a wired USB connection, to the WSEdevice, e.g., via a hub integrated into the WSE device.

According to this example, the endpoint may be uniquely identified bythe WSE host. For example, a combination of a WSE device address of theWSE device and a WSE EP handle assigned to the endpoint may uniquelyidentify a USB device endpoint within a WSE service set.

In other examples, the first and second devices may include any other,e.g., non-WSE and/or non-USB, device and the endpoint may perform thefunctionality of any other, e.g., non-USB and/or non-WSE, element.

Reference is now made to FIG. 1, which schematically illustrates a blockdiagram of a system 100, in accordance with some demonstrativeembodiments.

As shown in FIG. 1, in some demonstrative embodiments, system 100 mayinclude a communication network including one or more communicationdevices, e.g., communication devices 102 and/or 104, capable ofcommunicating content, data, information and/or signals over acommunication medium, for example, a radio channel, an IR channel, a RFchannel, a Wireless Fidelity (WiFi) channel, and the like. One or moreelements of system 100 may optionally be capable of communicating overany suitable wired communication links.

In some demonstrative embodiments, devices 102 and/or 104 may include,for example, a PC, a desktop computer, a mobile computer, a laptopcomputer, a notebook computer, a tablet computer, an Ultrabook™computer, a server computer, a media center, a mobile internet device, ahandheld computer, a handheld device, a storage device, a mass storagedevice, a USB mass storage (UMS) device, a hard drive, an optical drive,a flash memory device, a PDA device, a handheld PDA device, an on-boarddevice, an off-board device, a hybrid device (e.g., combining cellularphone functionalities with PDA device functionalities), a consumerdevice, a vehicular device, a non-vehicular device, a mobile or portabledevice, a non-mobile or non-portable device, a mobile phone, a cellulartelephone, a PCS device, a PDA device which incorporates a wirelesscommunication device, a mobile or portable GPS device, a DVB device, arelatively small computing device, a non-desktop computer, a “CarrySmall Live Large” (CSLL) device, an Ultra Mobile Device (UMD), an UltraMobile PC (UMPC), a Mobile Internet Device (MID), an “Origami” device orcomputing device, a device that supports Dynamically ComposableComputing (DCC), a context-aware device, a video device, an audiodevice, an A/V device, a Set-Top-Box (STB), a Blu-ray disc (BD) player,a BD recorder, a Digital Video Disc (DVD) player, a High Definition (HD)DVD player, a DVD recorder, a HD DVD recorder, a Personal Video Recorder(PVR), a broadcast HD receiver, a video source, an audio source, a videosink, an audio sink, a stereo tuner, a broadcast radio receiver, a flatpanel display, a Personal Media Player (PMP), a digital video camera(DVC), a digital audio player, a speaker, an audio receiver, an audioamplifier, a gaming device, a data source, a data sink, a Digital Stillcamera (DSC), a media player, a Smartphone, a television, a musicplayer, or the like.

In some demonstrative embodiments, devices 102 and/or 104 may includenetwork interfaces 110 and 120, respectively, to perform communicationover a communication network between communication devices 102 and 104and/or with one or more other devices, e.g., as described below.

Devices 102 and/or 104 may also include, for example, one or more of aprocessor 191, an input unit 192, an output unit 193, a memory unit 194,and a storage unit 195. Wireless communication devices 102 and/or 104may optionally include other suitable hardware components and/orsoftware components. In some demonstrative embodiments, some or all ofthe components of one or more of wireless communication devices 102and/or 104 may be enclosed in a common housing or packaging, and may beinterconnected or operably associated using one or more wired orwireless links. In other embodiments, components of one or more ofwireless communication devices 102 and/or 104 may be distributed amongmultiple or separate devices.

Processor 191 includes, for example, a Central Processing Unit (CPU), aDigital Signal Processor (DSP), one or more processor cores, asingle-core processor, a dual-core processor, a multiple-core processor,a microprocessor, a host processor, a controller, a plurality ofprocessors or controllers, a chip, a microchip, one or more circuits,circuitry, a logic unit, an Integrated Circuit (IC), anApplication-Specific IC (ASIC), or any other suitable multi-purpose orspecific processor or controller. Processor 191 executes instructions,for example, of an Operating System (OS) of wireless communicationdevices 102 and/or 104 and/or of one or more suitable applications.

Input unit 192 includes, for example, a keyboard, a keypad, a mouse, atouch-screen, a touch-pad, a track-ball, a stylus, a microphone, orother suitable pointing device or input device. Output unit 193includes, for example, a monitor, a screen, a touch-screen, a flat paneldisplay, a Cathode Ray Tube (CRT) display unit, a Liquid Crystal Display(LCD) display unit, a plasma display unit, one or more audio speakers orearphones, or other suitable output devices.

Memory unit 194 includes, for example, a Random Access Memory (RAM), aRead Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM(SD-RAM), a flash memory, a volatile memory, a non-volatile memory, acache memory, a buffer, a short term memory unit, a long term memoryunit, or other suitable memory units. Storage unit 195 includes, forexample, a hard disk drive, a floppy disk drive, a Compact Disk (CD)drive, a CD-ROM drive, a DVD drive, or other suitable removable ornon-removable storage units. Memory unit 194 and/or storage unit 195,for example, may store data processed by wireless communication devices102 and/or 104.

In some demonstrative embodiments, network interfaces 110 and/or 120 mayinclude wireless communication units, e.g., including radios 111 and121, to communicate over a wireless communication medium. For example,radios 111 and/or 121 may include, or may be associated with, one ormore antennas 107 and/or 108, respectively. Antennas 107 and/or 108 mayinclude any type of antennas suitable for transmitting and/or receivingwireless communication signals, blocks, frames, transmission streams,packets, messages and/or data. For example, antennas 107 and/or 108 mayinclude any suitable configuration, structure and/or arrangement of oneor more antenna elements, components, units, assemblies and/or arrays.Antennas 107 and/or 108 may include, for example, antennas suitable fordirectional communication, e.g., using beamforming techniques. Forexample, antennas 107 and/or 108 may include a phased array antenna, asingle element antenna, a set of switched beam antennas, and/or thelike. In some embodiments, antennas 107 and/or 108 may implementtransmit and receive functionalities using separate transmit and receiveantenna elements. In some embodiments, antennas 107 and/or 108 mayimplement transmit and receive functionalities using common and/orintegrated transmit/receive elements.

In some demonstrative embodiments, radios 111 and/or 121 may include oneor more wireless transmitters, receivers and/or transceivers able tosend and/or receive wireless communication signals, RF signals, frames,blocks, transmission streams, packets, messages, data items, and/ordata. For example, radios 111 and/or 121 may include or may beimplemented as part of a wireless Network Interface Card (NIC), and thelike.

In some demonstrative embodiments, devices 102 and 104 may establish acommunication link 103. Link 103 may be configured for communicationover a data link layer, e.g., the MAC layer, a logical link control(LLC) and/or a transport layer. Link 103 may include an uplink and/or adownlink. For example, the uplink may include a link for communicatingdata from device 104 to device 102, and/or the downlink may include alink for communicating data from device 102 to device 104. The downlinkmay include, for example, a unidirectional link from an AP to one ormore non-AP stations (STAs) or a unidirectional link from a non-APDestination STA to a non-AP Source STA. The uplink may include, forexample, a unidirectional link from a non-AP STA to an AP or aunidirectional link from a non-AP Source STA to a non-AP DestinationSTA.

In some demonstrative embodiments, link 103 may include a wirelesscommunication link, for example, a WiGig link, e.g., as described below.In other embodiments, link 103 may include any other wireless or wiredlink, e.g., an IP link. According to these embodiments, networkinterfaces 110 and/or 120 may include any suitable communication unit,e.g., a wired or wireless communication unit, to communicate over thecommunication network.

In some demonstrative embodiments, devices 102 and 104 may form, or maybe part of, a wireless communication network. The wireless communicationnetwork may include, for example, a P2P network or any other network.

In some demonstrative embodiments, devices 102 and/or 104 may performthe functionality of DMG stations (“DMG STA”). For example,communication devices 102 and/or 104 may be configured to communicateover the DMG band.

In some demonstrative embodiments, device 102 may include a mobiledevice and device 104 may include a docking device to connect device 102to one or more other devices (“peripherals”), for example, including oneor more USB devices, e.g., devices 162, 164, 166 and/or 168, and/or anyother device.

For example, device 102 may include, or may be included as part of amobile or portable device, for example, a mobile computer, a laptopcomputer, a notebook computer, a tablet computer, a Smartphone, ahandheld computer, a handheld device, a PDA device, a handheld PDAdevice, an on-board device, an off-board device, a hybrid device, e.g.,combining cellular phone functionalities with PDA devicefunctionalities, a consumer device, a vehicular device, a non-vehiculardevice, a cellular telephone, a PCS device, a PDA device whichincorporates a wireless communication device, a mobile or portable GPSdevice, a relatively small computing device, a non-desktop computer, aCSLL device, a UMD, a UMPC, a MID, an “Origami” device or computingdevice, a device that supports DCC, a context-aware device, a videodevice, an audio device, an A/V device, a data source, a Digital Stillcamera (DSC), a media player, or the like.

In one example, device 104 may include a docking device configured toconnect between device 102 and devices 162, 164, 166 and/or 168 via oneor more interfaces 139, for example, serial interfaces, e.g., USBinterfaces and/or any other interface. Devices 162, 164, 166 and/or 168may include for example, a mass storage device, e.g., a USB mass storage(UMS) device, a hard drive, an optical drive, a flash memory device, andthe like.

In some demonstrative embodiments, device 104 may be connected todevices 162, 164, 166 and/or 168 via one or more USB interfaces 139supporting one or more data transfer rates. For example, device 104 maybe connected to one or more of devices 162, 164, 166 and/or 168 via afirst USB interface 139 supporting a first data transfer rate, e.g., aUSB1.1 interface supporting a data transfer rate of 12 Mega bit persecond (Mbps), device 104 may be connected to one or more of devices162, 164, 166 and/or 168 via a second USB interface 139 supporting asecond data transfer rate, e.g., a USB2 interface supporting a data rateof 480 Mbps, and/or device 104 may be connected to one or more ofdevices 162, 164, 166 and/or 168 via a third USB interface 139supporting a third data transfer rate, e.g., a USB3 interface supportinga data transfer rate of up to 4.8 Giga bit per second (Gbps).

In some demonstrative embodiments, device 104 may include a hub 132,e.g., a USB hub, to connect between device 104 and one or more ofdevices 162, 164, 166 and 168. Additionally or alternatively, device 104may be connected to one or more of devices 162, 164, 166 and 168 via anyUSB tree, which may include, for example, one or more USB hubs 142. Forexample, device 102 may include, or may be connected to, one or more USBports, and each USB port may be connected to a USB device or be extendedto several ports via USB hub 132 and/or USB hub 142.

In some demonstrative embodiments, devices 162, 164, 166 and/or 168 mayperform the functionality of one or more Endpoints (EPs). For example, aUSB device may perform the functionality of one EP or more than one EP.In one example, device 162 may perform the functionality of an EP 134,device 164 may perform the functionality of an EP 135 and an EP 136,device 166 may perform the functionality of an EP 138, and/or device 168may perform the functionality of an EP 138.

In some demonstrative embodiments, device 102 may include a PALcommunication unit 130, and device 104 may include a PAL communicationunit 131. PAL communication units 103 and 131 may be configured tomanage a PAL connection between devices 102 and 104 over link 103.

In some demonstrative embodiments, devices 102 and 104 may communicateover link 103 according to a WiGig protocol.

In some demonstrative embodiments, devices 102 and 104 may be configuredfor communication of various dedicated services. For example, the WiGigtechnology is designed to carry multiple dedicated services, such asaudio-visual (A/V) and input output (I/O).

Some demonstrative embodiments are described herein with reference tocommunicating a data stream including USB data over a wirelesscommunication link according to a WSE protocol. However, otherembodiments may be implemented with respect to communicating any othersuitable data over any other communication link, according to any othercommunication protocol and/or over any other layer or PAL.

In some demonstrative embodiments, device 102 may perform thefunctionality of a USB host and device 104 may perform the functionalityof a USB device.

In some demonstrative embodiments, PAL communication unit 130 mayperform the functionality of a WSE host and PAL communication unit 131may perform the functionality of a WSE device.

In some demonstrative embodiments, PAL communication units 130 and 131may communicate USB traffic over the WSE PAL via link 103. The USBtraffic may include, for example, non-periodic (NP) traffic, e.g., bulkand/or control traffic, and/or periodic traffic, e.g., Isochronousand/or Interrupt traffic, which may be communicated by the EPs 134, 135,136, 138 and/or 140.

In some demonstrative embodiments, the periodic traffic may be requiredto be conducted under a certain bandwidth (BW) and latency Service LevelAgreement (SLA), while the NP traffic may be communicated according to abest-effort (BE), potentially “greedy”, scheme, which may be lesssensitive to latency. There may also be some, e.g., low, BW requirementsfor management and/or control traffic of the WSE PAL.

In some demonstrative embodiments, the USB traffic may include traffic(“USB IN”) delivered from the EPs the EPs 134, 135, 136, 138 and/or 140,via device 104, to device 102, and/or traffic (“USB OUT”) delivered fromdevice 102, via device 104, to the EPs the EPs 134, 135, 136, 138 and/or140.

In some demonstrative embodiments, the USB PAL may enable transport ofUSB data over media other than USB cable, for example, wireless links,e.g., Wi-Fi or WiGig links, or wired links, e.g., Ethernet. The USB PALmay directly interface with network interfaces 110 and 120, e.g., toreplace a network layer in the Open Systems Interconnection (OSI) model,or may be an IP application, interfacing with an IP (e.g., TCP/IP orUDP/IP) stack.

In some demonstrative embodiments, PAL communication unit 130 and PALcommunication unit 131 may be configured to enable media-agnosticconnectivity of a PAL between devices 102 and 104.

In some demonstrative embodiments, PAL communication unit 130 and PALcommunication unit 131 may be configured to enable connectivity of thePAL between devices 102 and 104 over a wireless communication link, forexample, a WiGig link, e.g., as described below. However, in otherembodiments, PAL communication unit 130 and PAL communication unit 131may be configured to enable media-agnostic connectivity of the PALbetween devices 102 and 104 over any other medium, for example, a Wi-Filink, an IP link, e.g., internet, Ethernet, over wire or wireless, andthe like.

In some demonstrative embodiments the USB PAL may replace a USB physicalcable.

In one example, PAL communication unit 130 may perform the functionalityof a host USB PAL and/or PAL communication unit 131 may perform thefunctionality of a device USB PAL.

For example, PAL communication units 130 and 131 may be configured tointerface, e.g., over link 103, between USB host logic, for example, aUSB driver at a host platform, e.g., a USB device interface (USBDI) ofdevice 102, e.g., a driver 137, and a USB controller of device 104.

According to this example, the combination of PAL communication unit130, network interface 110, network interface 120, and PAL communicationunit 131 may be configured to replace and/or emulate the USB physicalcable for connecting between a host device, e.g., device 102, and a USBdevice, e.g., included by or connected to device 104.

In some demonstrative embodiments, PAL communication units 130 and 131may be configured to communicate over a USB PAL between a USB host and aUSB device. The USB PAL may enable efficient transport of USB traffic bytransmitting USB transfers, as opposed to USB transactions. USBtransfers may include larger pieces of data, which may be moreappropriate for transmission over the wireless links.

However, built-in flow mechanisms for transport of data in USB may notbe used, for example, if USB link access mechanisms are not used by theUSB PAL.

In some demonstrative embodiments, the USB PAL may utilize a dedicatedUSB PAL transfer protocol, which may be configured to effectively handletransfer scenarios that may happen as in wired USB, including, forexample, an OUT transfer, which includes data to be transferred from theWSE host to a USB device, e.g., an endpoint of the USB device.

In some demonstrative embodiments, a wireless communication data rate ofcommunication link 103, which may be utilized for communication betweendevices 102 and 104, may be different from and/or not synchronized with,the data rate supported by the USB interfaces 139, which may be utilizedfor USB communication between device 104 and EPs 134, 135, 136, 138and/or 140.

In some demonstrative embodiments, device 104 may include a buffer 141,which may be configured to buffer data communicated between device 102and EPs 134, 135, 136, 138 and/or 140. For example, buffer 141 maybuffer data received from device 102 over link 103 and intended for anendpoint of EPs 134, 135, 136, 138 and/or 140 and/or hub 132, e.g.,until the data is successfully transferred from device 104 to theendpoint.

In some demonstrative embodiments, PAL communication units 130 and 131may utilize a flow control mechanism to manage the buffer space ofbuffer 141. For example, the flow control mechanism may be configured toensure that there is buffer space available on buffer 141 for the datathat is being transmitted, e.g., to avoid packet drop and/or waste ofthe resources utilized for transmission of the data between the devices102 and 104; and/or to ensure that there is no data on device 102waiting for transmission while there is buffer available in buffer 141.Buffer management may be especially critical, e.g., for wireless docks(wireless USB hubs), where the buffer space may be shared among multipleUSB devices.

In some demonstrative embodiments, data transfers (“transactions”)between device 104 and EPs 134, 135, 136, 138 and/or 140 may beinitiated by a host, e.g., by device 102. For example, device 102 mayinclude at least one driver 137, e.g., a USB device driver, configuredto transfer data between device 102 and EPs 134, 135, 136, 138 and/or140, e.g., via device 104.

In some demonstrative embodiments, driver 137 may trigger an INtransfer, e.g., a “read” transaction for reading data from an EP. Forexample, driver 137 may allocate a buffer in memory 194 to receive thedata transferred from the EP.

In some demonstrative, driver 137 may trigger an OUT transfer, e.g., a“write” transaction for writing data from device 102 to an EP. Forexample, driver 137 may send the data to device 104, e.g., over link,device 104 may buffer the data in buffer 141, and may transfer the datato the EP.

Some demonstrative embodiments are described herein with reference tocommunicating a data stream including USB data over a wirelesscommunication link according to a WSE protocol. However, otherembodiments may be implemented with respect to communicating any othersuitable data over any other communication link, according to any othercommunication protocol and/or over any other layer or PAL.

In some demonstrative embodiments, PAL communication unit 130 may sendthe OUT EP transaction data intended for an EP as part of one or moretransfer request (“TransferReq” or “T.req”) messages transmitted fromdevice 102 to device 104 over communication link 103. For example, theOUT EP transaction data may be fragmented into a plurality of datablocks to be transmitted as part of a respective plurality of transferrequest messages.

In some demonstrative embodiments, PAL communication unit 131 may beconfigured to control a data flow of a stream of data from device 102 todevice 104 over communication link 103. The stream of data may include,for example, data to be delivered to endpoints 134, 135, 136, 138 and/or140.

In some demonstrative embodiments, PAL communication units 130 and 131may be configured to utilize one or more buffer management and/or flowcontrol mechanisms, in which PAL communication unit 131 may dynamicallyreport to PAL communication unit 130 the available buffer space for anendpoint (flow), e.g., for each of endpoints 134, 135, 136, 138 and 140.PAL communication unit 130 may use the reported buffer space to flowcontrol and regulate the traffic targeted for the endpoint.

In some demonstrative embodiments, the dynamic and accurate tracking ofthe available buffer space on device 104, which may be required toensure high performance, may impose complexity on devices 102 and/or104, e.g., which may have, in some implementations, relatively lowprocessing power and/or limited capabilities.

In some demonstrative embodiments, PAL communication unit 131 mayutilize a credit allocation mechanism to allocate buffer 141 forbuffering data to be delivered to endpoints 134, 135, 136, 138 and/or140. For example, PAL communication unit 131 may allocate to PALcommunication unit 130 a plurality of credit allocations (“credits”)corresponding to a plurality of endpoints intended to receive data fromdevice 102 via link 103. Device 102 may transmit the data stream todevice 104 via link 103 according to the allocated credit, e.g., asdescribed below.

The term “credit” as used herein may refer to any suitable indication ofa permitted amount of data, which is permitted by a first device, fortransferring data from a second device to the first device. The creditmay include any suitable indication of the permitted amount of data.

In some demonstrative embodiments, PAL communication unit 131 mayallocate the credit in the form of a number of credit consumption units(CCUs), each CCU representing a predefined data size, for example, interms of bytes (b), e.g., 512b, or any other data size.

For example, PAL communication unit 131 may allocate to PALcommunication unit 130 credit for communicating data intended for an EP,e.g., by allocating to PAL communication unit 130 a number of CCUsrepresenting an amount of data intended for the EP, which PALcommunication unit 130 is permitted to communicate to PAL communicationunit 131 over communication link 103.

In some demonstrative embodiments, a transfer request message mayinclude, for example, a data block of the OUT transfer data fro an EP,an EP identifier (ID) identifying the EP intended to receive the datablock, and a Request identifier (RequestlD) identifying the data block,e.g., in relation to one or more other data blocks of the OUT transferdata. The transfer request message may also include an indication(RemSize) of remaining data size of the OUT transfer data to betransmitted as part of one or more subsequent transfer request messages.In other embodiments, the transfer request message may have any otherstructure and/or may include any other alternative and/or additionalinformation.

In some demonstrative embodiments, PAL communication unit 131 may sendto PAL communication unit 130 a transfer response message(“TransferResp” or “T.Rsp”) in response to the transfer request message.The transfer response message may include an indication of the creditallocated to the EP of the requested transfer.

In some demonstrative embodiments, the buffer size of buffer 141 may belimited, expensive and/or relatively small. Accordingly, efficientutilization of buffer 141 may enable increasing a throughput of the dataflow over link 103, increasing a throughput of the data flow betweendevice 102 and endpoints 134, 135, 136, 138 and/or 140, reducing alatency of the data flow between device 102 and endpoints 134, 135, 136,138 and/or 140, and/or reducing a production cost of device 104.

In one example, device 102 may be required to defer transmission of datato device 104 over communication link 103, e.g., if a size of the datato be transmitted is greater than an allocated credit corresponding toan endpoint intended to receive the data. Increasing the utilizationefficiency of buffer 141 may enable allocating greater credit to theendpoint and, accordingly, may reduce a latency of transferring the datafrom device 102 to the endpoint.

In some demonstrative embodiments, PAL communication unit 131 mayprovide the CCU to PAL communication unit 130, e.g., as part of acapability exchange procedure, which may be part of a sessionestablishment process between PAL communication units 130 and 131, e.g.,following the establishment of communication link 103.

In some demonstrative embodiments, buffer management of buffer 141 maybe performed per USB endpoint, e.g., per endpoints 134, 135, 136, 138and 140.

In some demonstrative embodiments, one or more different endpoints,e.g., endpoints 134, 135, 136, 138 and 140, may have differentrequirements and/or traffic characteristics.

In some demonstrative embodiments, using a common CCU value for allendpoints may result in inefficient use of the buffer space of buffer141.

In one example, a first endpoint, e.g., endpoint 135, may include anendpoint characterized by traffic of a reduced size, e.g., a controlendpoint; and a second endpoint, e.g., endpoint 136, may include anendpoint characterized by traffic of an increased size. For example, thetraffic to endpoint 135 may be characterized by a data size of up to 4Kilobyte (Kb), and/or the traffic to endpoint 135 may be characterizedby a data size of at least 16 kB.

Accordingly, it may be beneficial to manage the traffic to the firstendpoint according to a first CCU, and to manage the traffic to thesecond endpoint according to a second CCU, e.g., such that the secondCCU is lesser than the first CCU. For example, it may be beneficial tomanage the traffic to endpoint 135 according to a first CCU, e.g., of512 bytes (b), and to manage the traffic to endpoint 136 according to asecond CCU, e.g., of 2048b.

In some demonstrative embodiments, PAL communication unit 131 may beconfigured to define a plurality of CCUs, e.g., including two or moredifferent CCUs, corresponding to a plurality of endpoints. In oneexample, PAL communication unit 131 may define at least two differentCCUs to be utilized for allocating credit with respect to endpoints 134,135, 136, 138 and/or 140.

In one example, PAL communication unit 131 may define a first CCU, e.g.,512b or any other CCU, to be utilized for credit allocation with respectto one or more first endpoints, e.g., a control endpoint, and a secondCCU, e.g., 2048b or any other CCU, to be utilized for credit allocationwith respect to one or more second endpoints, e.g., a high trafficendpoint.

In some demonstrative embodiments, PAL communication unit 131 maydetermine a CCU corresponding to an endpoint based on endpointinformation corresponding to the endpoint.

In some demonstrative embodiments, the endpoint information may include,for example, information relating to a stream type to be communicated tothe endpoint, e.g., a control stream, an audio stream, a video stream, aperiodic stream, a non-periodic stream, an isochronous (ISO) stream, anasynchronous stream, an internet-protocol (IP) stream, a high priorityIP stream, a low priority IP stream, a bulk stream, a Best Effort (BE)stream, a BOT stream, and/or any other stream; information relating to atraffic rate utilized by the endpoint; information relating to a size ofdata blocks to be communicated to the endpoint, and/or any otherinformation relating to one or more attributes of the endpoint, thedevice including the endpoint and/or the stream to be communicated tothe endpoint.

In some demonstrative embodiments, defining different CCU values withrespect to the endpoints, e.g., in an endpoint-specific manner, and/ordefining a low-overhead mechanism for reporting of the value of each CCUto the host, may enable efficient use of buffer 141.

In some demonstrative embodiments, PAL communication unit 131 may beconfigured to define the CCU per endpoint. In other embodiments, PALcommunication unit 131 may define the CCU per group of endpoints, oraccording to any other scheme.

In some demonstrative embodiments, defining the CCU per endpoint, mayenable PAL communication unit 131 to intelligently choose the CCU valueper requirements and/or traffic characteristics of the endpoint, forexample, such that usage of buffer 141 is optimized, e.g., whileensuring low complexity tracking of the buffer space for the endpoint.

In some demonstrative embodiments, PAL communication unit 131 may beconfigured to communicate to PAL communication unit 130 one or more CCUvalues defined with respect to one or more of endpoints 134, 135, 136,138 and 140. PAL communication unit 130 may utilize the CCUs withrespect to credit allocations form PAL communication unit 131.

In some demonstrative embodiments, the CCU corresponding to the endpointmay define a unit by which a WSE host, e.g., PAL communication unit 130,is to keep track of buffer space available on a buffer of a WSE device,e.g., buffer 141, for buffering data intended for the endpoint.

In some demonstrative embodiments, a WSE host and a WSE device, e.g.,PAL communication units 130 and 131, may communicate granted credit,which is allocated with respect to an endpoint. The granted credit maybe represented as a multiple of the CCU defined for the endpoint. Forexample, the granted credit may be represented by an integer numberrepresenting the number of CCUs.

In some demonstrative embodiments, PAL communication unit 130 mayreceive from PAL communication unit 131 the CCU defined with respect tothe endpoint, and may account for consumed credits for the endpoint inmultiples of the CCU, e.g., regardless of an amount of data to betransferred from device 102 to the endpoint.

In one example, a WSE device, e.g., PAL communication unit 131, mayreport to a WSE host, e.g., PAL communication unit 130, a CCU of 512bfor a particular endpoint. According to this example, the WSE host mayaccount, e.g., may always account, for used credits for the particularendpoint in units of 512b, e.g., regardless of the number of bytes to beactually transmitted by the WSE host to the particular endpoint. Forexample, a WSE payload of 2064 bytes may account for 5 CCUs.

In some demonstrative embodiments, PAL communication unit 131 may beconfigured to communicate with PAL communication unit 130 a CCU definedwith respect to an endpoint, e.g., as described below.

In some demonstrative embodiments, PAL communication unit 131 may beconfigured to communicate with PAL communication unit 130 two or moredifferent CCUs defined with respect to two or more endpoints.

In some demonstrative embodiments, PAL communication unit 131 may beconfigured to communicate with PAL communication unit 130 at least onemessage including at least one identifier of an endpoint and a CCUdefined with respect to the endpoint.

For example, PAL communication unit 131 may be configured to communicatewith PAL communication unit 130 at least one message including at leastone endpoint descriptor corresponding to at least one endpoint. Theendpoint descriptor may include, for example, a CCU defined with respectto the endpoint, e.g., as described below.

In some demonstrative embodiments, PAL communication unit 131 may beconfigured to communicate with PAL communication unit 130 at least onemessage including at least two different CCUs defined with respect aplurality of endpoints.

For example, PAL communication unit 131 may be configured to communicatewith PAL communication unit 130 at least one message including two ormore endpoint descriptors corresponding to two or more endpoints. Thetwo or more endpoint descriptors may include two or more different CCUsdefined with respect to the two or more endpoints.

In one example, PAL communication unit 131 may communicate with PALcommunication unit 130 a message including an endpoint descriptorcorresponding to endpoint 135 and including a CCU defined for endpoint135, and an endpoint descriptor corresponding to endpoint 136 andincluding a CCU defined for endpoint 136. The CCU defined for endpoint135 may be different from the CCU defined for endpoint 136.Alternatively, the descriptors corresponding to both endpoints 135 and136 may include the same CCU defined for both endpoints 135 and 136.

In some demonstrative embodiments, during an enumeration process of adevice, e.g., a USB device, of devices 162, 164, 166 and/or 168, PALcommunication unit 130 may request a handle to be allocated by PALcommunication unit 131 for endpoints, e.g., every endpoint, on thedevice.

For example, PAL communication unit 130 may transmit to PALcommunication unit 131 a message, e.g., an Endpoint Handle Request,requesting a handle to be allocated by PAL communication unit 131 forevery endpoint on a USB device.

In some demonstrative embodiments, PAL communication unit 131 may returnthe allocated endpoint handles to PAL communication unit 130, forexample, in response to the endpoint handle request, e.g., using anEndpoint Handle Response message.

In some demonstrative embodiments, PAL communication unit 131 may alsoinclude in the Endpoint Handle Response information required for USB PALoperations for the endpoints of the USB device.

In some demonstrative embodiments, PAL communication unit 130 mayinclude one or more CCUs defined for one or more endpoints of a device,e.g., as part of the Endpoint Handle Response message sent from PALcommunication unit 131 to PAL communication unit 130. In otherembodiments, PAL communication unit 130 may include the one or more CCUsas part of any other solicited or unsolicited message.

In one example, PAL communication unit 130 may transmit to PALcommunication unit 131 an Endpoint Handle Request to assign handles toendpoints of device 164. PAL communication unit 131 may transmit to PALcommunication unit 130 an Endpoint Handle Response message including anEP descriptor of EP 135, including the CCU defined for EP 135, and anendpoint descriptor of EP 136, including the CCU defined for EP 136.

In some demonstrative embodiments, at the time of session establishmentbetween PAL communication units 130 and 131, PAL communication unit 131may not necessarily have information regarding the number and/or type ofthe endpoints. Accordingly, the decision regarding the value of the CCUmay not be correlated with the requirements and/or trafficcharacteristics of the endpoints. This may result in reduced efficiency.

In some demonstrative embodiments, PAL communication unit 131 may beconfigured to learn about the devices, e.g., USB devices and/orendpoints, which are “behind” the PAL communication unit 131 (beingmanaged by the USB PAL), e.g., in a low complexity manner.

In some demonstrative embodiments, learning the device type and/orcharacteristics may help PAL communication unit 131 to make intelligentdecisions regarding the resources to be allocated to the devices, whichmay further lead to higher efficiency.

In some demonstrative embodiments, it may not be efficient to configurePAL communication unit 131 to learn about USB device type andcapabilities, for example, by examining control transfers, e.g., USBcontrol transfers, that are tunneled as data packets between PALcommunication unit 130 and PAL communication unit 131.

For example, examining the USB control transfers, e.g., in order to findthe commands asking for the device descriptor of the USB device, andthen reading the device descriptor in the payload of the response mayincur, for example, high overhead.

In some demonstrative embodiments, PAL communication unit 130 may beconfigured to explicitly communicate to PAL communication unit 131 adevice descriptor, e.g., a USB device descriptor, of a device, e.g., aUSB device, including the endpoints, for example, as part of an explicitmessage communicated to PAL communication unit 131. Explicitlycommunicating the device descriptor to PAL communication unit 131 may,for example, reduce the complexity associated with the process for PALcommunication unit 131 to learn the device type and/or characteristics.

In one example, a USB device descriptor corresponding to a USB devicemay include, for example, information relating to a type of the USBdevice, e.g., a storage device, a keyboard, a mouse, and the like;information relating to a communication protocol utilized by the device,e.g., the USB 2.0 protocol, the USB 3.0 protocol, and the like; and/orany other information. The device descriptor may include for example, aUSB device descriptor, e.g., as defined by the USB 2.0 and/or USB 3.0Specifications.

In some demonstrative embodiments, PAL communication unit 130 may beconfigured to use a low overhead mechanism to communicate the devicedescriptor to PAL communication unit 131, e.g., as described below.

In some demonstrative embodiments, PAL communication unit 130 may beconfigured to include the USB device descriptor in a packet communicatedby PAL communication unit 130 to PAL communication unit 131, e.g.,during the enumeration process.

In some demonstrative embodiments, PAL communication unit 130 may beconfigured to include the USB device descriptor in a packet communicatedby PAL communication unit 130 to PAL communication unit 131, e.g.,following a step through which the PAL communication unit 130 learns thedevice descriptor and, for example, before the endpoint handles arerequested from the PAL communication unit 131.

In some demonstrative embodiments, PAL communication unit 130 may beconfigured to include the USB device descriptor as part of an UpdateDevice Request message transmitted from PAL communication unit 130 toPAL communication unit 131.

In some demonstrative embodiments, PAL communication unit 130 maycommunicate to PAL communication unit 131 a control transfer request forcontrol information including a device descriptor of a device of devices162, 164, 166 and 168. PAL communication unit 131 may communicate to PALcontrol unit 130 a control transfer response including the controlinformation, and PAL communication unit 130 may communicate a message,e.g., an update device request, including the device descriptor, whichwas included in the control information.

Reference is made to FIG. 2, which schematically illustrates a sequenceof communications between a WSE host 202, and a WSE device 204, inaccordance with some demonstrative embodiments. For example, PALcommunication unit 130 (FIG. 1) may perform the functionality of WSEhost 202, and/or PAL communication unit 131 (FIG. 1) may perform thefunctionality of WSE device 204.

In some demonstrative embodiments, WSE host 202 and WSE device 204 mayestablish a session 210.

In some demonstrative embodiments, WSE host 202 and WSE device 204 mayperform an enumeration procedure 212, e.g., after the session 210 isestablished.

In some demonstrative embodiments, during the enumeration procedure WSEhost 202 transmitting one or more control transfer requests 214 to WSEdevice 204. The control transfer requests 214 may include requests toone or more USB devices connected to WSE device 204 to provide USBdescriptors of the USB devices. The USB descriptors may be tunneled byWSE device 204 to WSE host 202.

In some demonstrative embodiments, during the enumeration procedure WSEdevice 204 may transmit one or more control transfer responses 216 toWSE host 202. The control transfer responses 216 may include the devicedescriptors 217 of the USB devices.

In some demonstrative embodiments, WSE host 202 may transmit to WSEdevice 204 one or more messages explicitly including the USB devicedescriptors of one or more USB devices.

In some demonstrative embodiments, WSE host 202 may transmit to WSEdevice 204 at least one Update Device Request message 218 including theUSB device descriptor 219 of at least one USB device. Device descriptor219 may be included, for example, in a device descriptor portion having,for example, a width of 18 bytes.

In some demonstrative embodiments, WSE device 204 may transmit an UpdateDevice Response message 220, e.g., in response to the Update DeviceRequest message 218.

In some demonstrative embodiments, WSE host 202 may transmit to WSEdevice 204 an endpoint handle request message 222. The endpoint handlerequest message 222 may include, for example, a list of endpointdescriptors corresponding to a plurality of endpoints.

Alternatively, WSE host 202 may transmit to WSE device 204 a pluralityof endpoint handle request messages 222 including the endpointdescriptors corresponding to the plurality of endpoints.

In some demonstrative embodiments, WSE device 204 may determine one ormore endpoint-specific values, e.g., a plurality of CCU values, to bedefined with respect to the plurality of endpoints. WSE device 204 maydetermine the CCU values, for example, based on the endpoint descriptorscorresponding to the plurality of endpoints.

In some demonstrative embodiments, WSE device 204 may determine one ormore of the CCU values to be defined with respect to the plurality ofendpoints based on the USB device descriptors and/or any otherinformation, e.g., as described above.

In some demonstrative embodiments, WSE device 204 may transmit to WSEhost 202 an endpoint handle response 224 including the plurality of CCUvalues defined with respect to the plurality of endpoints, e.g., in theform of an EP CCU list 223. Alternatively, WSE device 204 may transmitto WSE host 202 a plurality of endpoint handle responses 224 includingthe plurality of CCU values.

Reference is made to FIG. 3, which schematically illustrates a method ofcontrolling data flow, in accordance with some demonstrativeembodiments. In some embodiments, one or more of the operations of themethod of FIG. 3 may be performed by a system, e.g., system 100 (FIG.1); a device, e.g., device 102 (FIG. 1) and/or device 104 (FIG. 1); aPAL communication unit, e.g., PAL communication unit 130 (FIG. 1) and/orPAL communication unit 131 (FIG. 1); a WSE host, e.g., WSE host 202(FIG. 2); and/or a WSE device, e.g., WSE device 204 (FIG. 2).

As indicated at block 302, the method may include controlling thetransfer of a stream of data, including data to be delivered to aplurality of endpoints, from a first device to a second device over acommunication link. For example, PAL communication units 130 and 131(FIG. 1) may control the transfer of a stream of data including dataintended for endpoints 134, 135, 136, 138 and/or 140 (FIG. 1) fromdevice 102 (FIG. 1) to device 104 (FIG. 1), e.g., as described above.

As indicated at block 304, controlling the transfer of the stream ofdata may include communicating between the first and second devices atleast one endpoint-specific CCU defined with respect to at least oneendpoint. For example, PAL communication unit 131 (FIG. 1) may transmitto PAL communication unit 130 (FIG. 1) at least one message including atleast one CCU defined with respect to at least one endpoint of endpoints134, 135, 136, 138 and/or 140 (FIG. 1), e.g., as described above.

As indicated at block 306, communicating the CCU may includecommunicating at least one message including at least one endpointdescriptor corresponding to the at least one endpoint, the endpointdescriptor including the defined with respect to the endpoint. Forexample, WSE device 204 (FIG. 2) may transmit to WSE host 202 (FIG. 2)endpoint handle response 224 (FIG. 2) including the CCU defined withrespect to the endpoint, e.g., as described above.

As indicated at block 308, communicating the message may includecommunicating a message including two or more CCUs defined with respectto two or more endpoints. For example, WSE device 204 (FIG. 2) maytransmit to WSE host 202 (FIG. 2) endpoint handle response 224 (FIG. 2)including EP CCU list 223 (FIG. 2), e.g., as described above.

As indicated at block 310, controlling the transfer of the stream ofdata may include communicating a message including granted credit, whichis allocated with respect to the endpoint and represented as a multipleof the CCU defined for the endpoint. For example, PAL communication unit131 (FIG. 1) may transmit to PAL communication unit 130 (FIG. 1) amessage allocating credit for the endpoint as a multiple of the CCUdefined for the endpoint, e.g., as described above.

As indicated at block 312, controlling the transfer of the stream ofdata may include accounting for consumed credits for the endpoint inmultiples of the CCU. For example, PAL communication unit 130 (FIG. 1)may account for data transferred to the endpoint based on the CCUdefined for the endpoint, e.g., regardless of an amount of data to betransferred to the endpoint, as described above.

As indicated at block 314, controlling the transfer of the stream ofdata may include communicating from the first device to the seconddevice a device descriptor of at least one device including at least oneendpoint. For example, PAL communication unit 130 (FIG. 1) may transmitto PAL communication unit 131 (FIG. 1) at least one message explicitlyincluding the device descriptor of a USB device, e.g., as describedabove.

As indicated at block 316, communicating the device descriptor mayinclude communicating at least one control transfer request from thefirst device to the second device. For example, the control transferrequest may include a request to the second device to transfer to thefirst device control information including the device descriptor of adevice. For example, WSE host 202 (FIG. 2) may transmit to WSE device204 (FIG. 2) control transfer request 214 (FIG. 2), e.g., as describedabove.

As indicated at block 318, communicating the device descriptor mayinclude communicating at least one control transfer response from thesecond device to the first device, the control transfer responseincluding the control information. For example, WSE device 204 (FIG. 2)may transmit to WSE host 202 (FIG. 2) control transfer response 216(FIG. 2) including device descriptor 217 (FIG. 2), e.g., as describedabove.

As indicated at block 320, communicating the device descriptor mayinclude communicating at least one update device request from the firstdevice to the second device, the update device request including thedevice descriptor. For example, WSE host 202 (FIG. 2) may transmit toWSE device 204 (FIG. 2) update device request 219 (FIG. 2) includingdevice descriptor 219 (FIG. 2), e.g., as described above.

As indicated at block 322, controlling the transfer of the stream ofdata may include defining the CCU corresponding to the endpoint based onthe device descriptor. For example, PAL communication unit 131 (FIG. 1)may define the CCU of the endpoint based on the device descriptorreceived from PAL communication unit 131 (FIG. 1), e.g., as describedabove.

Reference is made to FIG. 4, which schematically illustrates a productof manufacture 400, in accordance with some demonstrative embodiments.Product 400 may include a non-transitory machine-readable storage medium402 to store logic 404, which may be used, for example, to perform atleast part of the functionality of device 102 (FIG. 1), device 104 (FIG.1), PAL communication unit 130 (FIG. 1), and/or PAL communication unit131 (FIG. 1), to perform one or more of the operations FIG. 2, and/or toperform one or more operations of the method of FIG. 3. The phrase“non-transitory machine-readable medium” is directed to include allcomputer-readable media, with the sole exception being a transitorypropagating signal.

In some demonstrative embodiments, product 400 and/or machine-readablestorage medium 402 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage medium 402 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 404 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 404 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Matlab,Pascal, Visual BASIC, assembly language, machine code, and the like.

EXAMPLES

The following examples pertain to further embodiments.

Example 1 includes an apparatus comprising a communication unit tocommunicate data between a first device and a second device over acommunication link, the data including data to be delivered from thefirst device to a plurality of endpoints via the second device, whereinthe communication unit is to communicate between the first and seconddevices at least one message including at least one endpoint descriptorcorresponding to at least one endpoint of the plurality of endpoints,the endpoint descriptor including a credit consumption unit (CCU)defined with respect to the endpoint.

Example 2 includes the subject matter of Example 1 and optionally,wherein the message includes two or more endpoint descriptorscorresponding to two or more endpoints of the plurality of endpoints,and wherein the two or more endpoint descriptors include two or moredifferent CCUs defined with respect to the two or more endpoints.

Example 3 includes the subject matter of Example 1 or 2 and optionally,wherein the CCU defines a unit by which the first device is to keeptrack of buffer space available on the second device for buffering datafor the endpoint.

Example 4 includes the subject matter of any one of Examples 1-3 andoptionally, wherein the communication unit is to receive the message andto account for consumed credits for the endpoint in multiples of theCCU, regardless of an amount of data to be transferred from the firstdevice to the endpoint.

Example 5 includes the subject matter of any one of Examples 1-3 andoptionally, wherein the communication unit is to transmit the messageand to transmit a message including granted credit, which is allocatedwith respect to the endpoint, the granted credit is represented as amultiple of the CCU.

Example 6 includes the subject matter of any one of Examples 1-5 andoptionally, wherein the communication unit is to communicate between thesecond and first devices a message including granted credit, which isallocated with respect to the endpoint, wherein the granted credit isrepresented as a multiple of the CCU.

Example 7 includes the subject matter of any one of Examples 1-6 andoptionally, wherein the message includes an endpoint handle response.

Example 8 includes the subject matter of Example 7 and optionally,wherein the communication unit is to communicate at least one endpointhandle request from the first device to the second device, the endpointhandle request including an endpoint descriptor of the endpoint, andwherein the endpoint handle response includes the CCU of the endpoint.

Example 9 includes the subject matter of any one of Examples 1-8 andoptionally, wherein the communication unit is to communicate an updatedevice request from the first device to the second device, the updatedevice request including a device descriptor of a Universal-Serial-Bus(USB) device including the endpoint.

Example 10 includes the subject matter of Example 9 and optionally,wherein the communication unit is to define the CCU based on the devicedescriptor.

Example 11 includes the subject matter of any one of Examples 1-10 andoptionally, wherein the communication unit is to communicate a controltransfer request from the first device to the second device, the controltransfer request requesting the second device to transfer to the firstdevice control information including a device descriptor of a deviceincluding one or more of the plurality of endpoints, wherein thecommunication unit is to communicate a control transfer response fromthe second device to the first device, the control transfer responseincluding the control information, and wherein the communication unit isto communicate an update device request from the first device to thesecond device, the update device request including the devicedescriptor.

Example 12 includes the subject matter of any one of Examples 1-11 andoptionally, wherein the first device comprises a host Universal SerialBus (USB) Protocol Adaptation Layer (PAL), and wherein the second devicecomprises a Device USB PAL.

Example 13 includes the subject matter of any one of Examples 1-12 andoptionally, wherein the communication link comprises a wirelesscommunication link.

Example 14 includes the subject matter of Example 13 and optionally,wherein the wireless communication link comprises a wireless gigabit(WiGig) link.

Example 15 includes the subject matter of any one of Examples 1-14 andoptionally, wherein the first device comprises a WiGig Serial Extension(WSE) host, and wherein the second device comprises a WSE Device.

Example, 16 includes an apparatus of communicating data, the apparatuscomprising a communication unit to communicate data between a firstdevice and a second device over a communication link, the data includingdata to be delivered from the first device to a plurality of endpointsvia the second device, the communication unit is to communicate from thefirst device to the second device a message including a devicedescriptor of at least one device including at least one endpoint.

Example 17 includes the subject matter of Example 16 and optionally,wherein the device descriptor indicates one or more characteristics ofthe device including the endpoint.

Example 18 includes the subject matter of Example 16 or 17 andoptionally, wherein the communication unit is to communicate at leastone control transfer request from the first device to the second device,the control transfer request to request the second device to transfer tothe first device control information including a device descriptor ofthe device including the endpoint, and wherein the communication unit isto communicate at least one control transfer response from the seconddevice to the first device, the control transfer response including thecontrol information.

Example 19 includes the subject matter of any one of Examples 16-18 andoptionally, wherein the communication unit is to communicate at leastone update device request from the first device to the second device,the update device request including the device descriptor.

Example 20 includes the subject matter of any one of Examples 16-19 andoptionally, wherein the communication unit is to communicate between thefirst and second devices at least one message including at least oneendpoint descriptor corresponding to the at least one endpoint, theendpoint descriptor including a credit consumption unit (CCU) definedwith respect to the endpoint.

Example 21 includes the subject matter of Example 20 and optionally,wherein the CCU is based on the device descriptor.

Example 22 includes the subject matter of any one of Examples 16-21 andoptionally, wherein the first device comprises a host Universal SerialBus (USB) Protocol Adaptation Layer (PAL), and wherein the second devicecomprises a Device USB PAL.

Example 23 includes the subject matter of any one of Examples 16-22 andoptionally, wherein the communication link comprises a wirelesscommunication link.

Example 24 includes the subject matter of Example 23 and optionally,wherein the wireless communication link comprises a wireless gigabit(WiGig) link.

Example 25 includes the subject matter of any one of Examples 16-24 andoptionally, wherein the first device comprises a WiGig Serial Extension(WSE) host, and wherein the second device comprises a WSE Device.

Example 26 includes a communication system comprising a devicecomprising:

a network interface to communicate over a network; and a wirelessgigabit (WiGig) Serial Extension (WSE) controller to perform thefunctionality of a WSE host or a WSE device to communicate UniversalSerial Bus (USB) data between a USB host and a USB device over thenetwork, the data including data to be delivered from the USB host to aplurality of endpoints of the USB device, wherein the WSE controller isto communicate between the host and WSE device at least one messageincluding at least one endpoint descriptor corresponding to at least oneendpoint of the plurality of endpoints, the endpoint descriptorincluding a credit consumption unit (CCU) defined with respect to theendpoint.

Example 27 includes the subject matter of Example 26 and optionally,wherein the message includes two or more endpoint descriptorscorresponding to two or more endpoints of the plurality of endpoints,and wherein the two or more endpoint descriptors include two or moredifferent CCUs defined with respect to the two or more endpoints.

Example 28 includes the subject matter of Example 26 or 27 andoptionally, wherein the CCU defines a unit by which the WSE host is tokeep track of buffer space available on the WSE device for bufferingdata for the endpoint.

Example 29 includes the subject matter of any one of Examples 26-28 andoptionally, wherein the WSE controller is to receive the message and toaccount for consumed credits for the endpoint in multiples of the CCU,regardless of an amount of data to be transferred from the WSE host tothe endpoint.

Example 30 includes the subject matter of any one of Examples 26-29 andoptionally, wherein the WSE controller is to transmit the message and totransmit a message including granted credit, which is allocated withrespect to the endpoint, the granted credit is represented as a multipleof the CCU.

Example 31 includes the subject matter of any one of Examples 26-30 andoptionally, wherein the WSE controller is to communicate between the WSEdevice and WSE host a message including granted credit, which isallocated with respect to the endpoint, wherein the granted credit isrepresented as a multiple of the CCU.

Example 32 includes the subject matter of any one of Examples 26-31 andoptionally, wherein the message includes an endpoint handle response.

Example 33 includes the subject matter of Example 32 and optionally,wherein the WSE controller is to communicate at least one endpointhandle request from the WSE host to the WSE device, the endpoint handlerequest including an endpoint descriptor of the endpoint, and whereinthe endpoint handle response includes the CCU of the endpoint.

Example 34 includes the subject matter of any one of Examples 26-33 andoptionally, wherein the WSE controller is to communicate an updatedevice request from the WSE host to the WSE device, the update devicerequest including a device descriptor of the USB device.

Example 35 includes the subject matter of Example 34 and optionally,wherein the WSE controller is to define the CCU based on the devicedescriptor.

Example 36 includes the subject matter of any one of Examples 26-35 andoptionally, wherein the WSE controller is to communicate a controltransfer request from the WSE host to the WSE device, the controltransfer request requesting the WSE device to transfer to the WSE hostcontrol information including a device descriptor of a device includingone or more of the plurality of endpoints, wherein the WSE controller isto communicate a control transfer response from the WSE device to theWSE host, the control transfer response including the controlinformation, and wherein the WSE controller is to communicate an updatedevice request from the WSE host to the WSE device, the update devicerequest including the device descriptor.

Example 37 includes the subject matter of any one of Examples 26-36 andoptionally, wherein the network interface comprises a wirelesscommunication unit.

Example 38 includes a communication system comprising a devicecomprising a network interface to communicate over a network; and awireless gigabit (WiGig) Serial Extension (WSE) controller to performthe functionality of a WSE host or a WSE device to communicate UniversalSerial Bus (USB) data between a USB host and a USB device over thenetwork, the data including data to be delivered from the USB host to aplurality of endpoints of the USB device, wherein the WSE controller isto communicate from the WSE host to the WSE device a message including adevice descriptor of the USB device.

Example 39 includes the subject matter of Example 38 and optionally,wherein the device descriptor indicates one or more characteristics ofthe USB device.

Example 40 includes the subject matter of Example 38 or 39 andoptionally, wherein the WSE controller is to communicate at least onecontrol transfer request from the WSE host to the WSE device, thecontrol transfer request to request the WSE device to transfer to theWSE host control information including a device descriptor of the USBdevice, and wherein the WSE controller is to communicate at least onecontrol transfer response from the WSE device to the WSE host, thecontrol transfer response including the control information.

Example 41 includes the subject matter of any one of Examples 38-40 andoptionally, wherein the WSE controller is to communicate at least oneupdate device request from the WSE host to the WSE device, the updatedevice request including the device descriptor.

Example 42 includes the subject matter of any one of Examples 38-41 andoptionally, wherein the WSE controller is to communicate between the WSEhost and WSE device at least one message including at least one endpointdescriptor corresponding to the at least one endpoint, the endpointdescriptor including a credit consumption unit (CCU) defined withrespect to the endpoint.

Example 43 includes the subject matter of Example 42 and optionally,wherein the CCU is based on the device descriptor.

Example 44 includes the subject matter of any one of Examples 38-43 andoptionally, wherein the network interface comprises a wirelesscommunication unit.

Example 45 includes a method of communication, the method comprisingcontrolling the transfer of a stream of data from a first device to asecond device over a communication link, the stream of data includingdata to be delivered to a plurality of endpoints, the controllingincluding communicating between the first and second devices at leastone message including at least one endpoint-specific credit consumptionunit (CCU) defined with respect to at least one endpoint of theplurality of endpoints.

Example 46 includes the subject matter of Example 45 and optionally,wherein the message includes two or more endpoint descriptorscorresponding to two or more endpoints of the plurality of endpoints,and wherein the two or more endpoint descriptors include two or moredifferent CCUs defined with respect to the two or more endpoints.

Example 47 includes the subject matter of Example 45 or 46 andoptionally, wherein the CCU defines a unit by which the first device isto keep track of buffer space available on the second device forbuffering data for the endpoint.

Example 48 includes the subject matter of any one of Examples 45-47 andoptionally, comprising receiving the message, and accounting forconsumed credits for the endpoint in multiples of the CCU, regardless ofan amount of data to be transferred from the first device to theendpoint.

Example 49 includes the subject matter of any one of Examples 45-48 andoptionally, comprising transmitting the message, and transmitting amessage including granted credit, which is allocated with respect to theendpoint, the granted credit is represented as a multiple of the CCU.

Example 50 includes the subject matter of any one of Examples 45-49 andoptionally, comprising communicating between the second and firstdevices a message including granted credit, which is allocated withrespect to the endpoint, wherein the granted credit is represented as amultiple of the CCU.

Example 51 includes the subject matter of any one of Examples 45-50 andoptionally, wherein the message includes an endpoint handle response.

Example 52 includes the subject matter of Example 51 and optionally,comprising communicating at least one endpoint handle request from thefirst device to the second device, the endpoint handle request includingan endpoint descriptor of the endpoint, and wherein the endpoint handleresponse includes the CCU of the endpoint.

Example 53 includes the subject matter of any one of Examples 45-52 andoptionally, comprising communicating an update device request from thefirst device to the second device, the update device request including adevice descriptor of a Universal-Serial-Bus (USB) device including theendpoint.

Example 54 includes the subject matter of Example 53 and optionally,comprising defining the CCU based on the device descriptor.

Example 55 includes the subject matter of any one of Examples 45-54 andoptionally, comprising communicating a control transfer request from thefirst device to the second device, the control transfer requestrequesting the second device to transfer to the first device controlinformation including a device descriptor of a device including one ormore of the plurality of endpoints; communicating a control transferresponse from the second device to the first device, the controltransfer response including the control information; and communicatingan update device request from the first device to the second device, theupdate device request including the device descriptor.

Example 56 includes the subject matter of any one of Examples 45-55 andoptionally, wherein the first device comprises a host Universal SerialBus (USB) Protocol Adaptation Layer (PAL), and wherein the second devicecomprises a Device USB PAL.

Example 57 includes the subject matter of any one of Examples 45-56 andoptionally, wherein the communication link comprises a wirelesscommunication link.

Example 58 includes the subject matter of Example 57 and optionally,wherein the wireless communication link comprises a wireless gigabit(WiGig) link.

Example 59 includes the subject matter of any one of Examples 45-58 andoptionally, wherein the first device comprises a WiGig Serial Extension(WSE) host, and wherein the second device comprises a WSE Device.

Example 60 includes a method of communication, the method comprisingcontrolling the transfer of a stream of data from a first device to asecond device over a communication network, the stream of data includingdata to be delivered to a plurality of endpoints, the controllingincluding communicating from the first device to the second device amessage including a device descriptor of at least one device includingat least one endpoint.

Example 61 includes the subject matter of Example 60 and optionally,wherein the device descriptor indicates one or more characteristics ofthe device including the endpoint.

Example 62 includes the subject matter of Example 60 or 61 andoptionally, comprising communicating at least one control transferrequest from the first device to the second device, the control transferrequest to request the second device to transfer to the first devicecontrol information including a device descriptor of the deviceincluding the endpoint; and communicating at least one control transferresponse from the second device to the first device, the controltransfer response including the control information.

Example 63 includes the subject matter of any one of Examples 60-62 andoptionally, comprising communicating at least one update device requestfrom the first device to the second device, the update device requestincluding the device descriptor.

Example 64 includes the subject matter of any one of Examples 60-63 andoptionally, comprising communicating between the first and seconddevices at least one message including at least one endpoint descriptorcorresponding to the at least one endpoint, the endpoint descriptorincluding a credit consumption unit (CCU) defined with respect to theendpoint.

Example 65 includes the subject matter of Example 64 and optionally,wherein the CCU is based on the device descriptor.

Example 66 includes the subject matter of any one of Examples 60-65 andoptionally, wherein the first device comprises a host Universal SerialBus (USB) Protocol Adaptation Layer (PAL), and wherein the second devicecomprises a Device USB PAL.

Example 67 includes the subject matter of any one of Examples 60-66 andoptionally, wherein the communication link comprises a wirelesscommunication link.

Example 68 includes the subject matter of Example 67 and optionally,wherein the wireless communication link comprises a wireless gigabit(WiGig) link.

Example 69 includes the subject matter of any one of Examples 60-68 andoptionally, wherein the first device comprises a WiGig Serial Extension(WSE) host, and wherein the second device comprises a WSE Device.

Example 70 includes a product including a non-transitory storage mediumhaving stored thereon instructions that, when executed by a machine,result in controlling the transfer of a stream of data from a firstdevice to a second device over a communication link, the stream of dataincluding data to be delivered to a plurality of endpoints, thecontrolling including communicating between the first and second devicesat least one message including at least one endpoint-specific creditconsumption unit (CCU) defined with respect to at least one endpoint ofthe plurality of endpoints.

Example 71 includes the subject matter of Example 70 and optionally,wherein the message includes two or more endpoint descriptorscorresponding to two or more endpoints of the plurality of endpoints,and wherein the two or more endpoint descriptors include two or moredifferent CCUs defined with respect to the two or more endpoints.

Example 72 includes the subject matter of Example 70 or 71 andoptionally, wherein the CCU defines a unit by which the first device isto keep track of buffer space available on the second device forbuffering data for the endpoint.

Example 73 includes the subject matter of any one of Examples 70-72 andoptionally, wherein the instructions result in receiving the message,and accounting for consumed credits for the endpoint in multiples of theCCU, regardless of an amount of data to be transferred from the firstdevice to the endpoint.

Example 74 includes the subject matter of any one of Examples 70-73 andoptionally, wherein the instructions result in transmitting the message,and transmitting a message including granted credit, which is allocatedwith respect to the endpoint, the granted credit is represented as amultiple of the CCU.

Example 75 includes the subject matter of any one of Examples 70-74 andoptionally, wherein the instructions result in communicating between thesecond and first devices a message including granted credit, which isallocated with respect to the endpoint, wherein the granted credit isrepresented as a multiple of the CCU.

Example 76 includes the subject matter of any one of Examples 70-75 andoptionally, wherein the message includes an endpoint handle response.

Example 77 includes the subject matter of Example 76 and optionally,wherein the instructions result in communicating at least one endpointhandle request from the first device to the second device, the endpointhandle request including an endpoint descriptor of the endpoint, andwherein the endpoint handle response includes the CCU of the endpoint.

Example 78 includes the subject matter of any one of Examples 70-77 andoptionally, wherein the instructions result in communicating an updatedevice request from the first device to the second device, the updatedevice request including a device descriptor of a Universal-Serial-Bus(USB) device including the endpoint.

Example 79 includes the subject matter of Example 78 and optionally,wherein the instructions result in defining the CCU based on the devicedescriptor.

Example 80 includes the subject matter of any one of Examples 70-79 andoptionally, wherein the instructions result in communicating a controltransfer request from the first device to the second device, the controltransfer request requesting the second device to transfer to the firstdevice control information including a device descriptor of a deviceincluding one or more of the plurality of endpoints; communicating acontrol transfer response from the second device to the first device,the control transfer response including the control information; andcommunicating an update device request from the first device to thesecond device, the update device request including the devicedescriptor.

Example 81 includes the subject matter of any one of Examples 70-80 andoptionally, wherein the first device comprises a host Universal SerialBus (USB) Protocol Adaptation Layer (PAL), and wherein the second devicecomprises a Device USB PAL.

Example 82 includes the subject matter of any one of Examples 70-81 andoptionally, wherein the communication link comprises a wirelesscommunication link.

Example 83 includes the subject matter of Example 82 and optionally,wherein the wireless communication link comprises a wireless gigabit(WiGig) link.

Example 84 includes the subject matter of any one of Examples 70-83 andoptionally, wherein the first device comprises a WiGig Serial Extension(WSE) host, and wherein the second device comprises a WSE Device.

Example 85 includes a product including a non-transitory storage mediumhaving stored thereon instructions that, when executed by a machine,result in controlling the transfer of a stream of data from a firstdevice to a second device over a communication network, the stream ofdata including data to be delivered to a plurality of endpoints, thecontrolling including communicating from the first device to the seconddevice a message including a device descriptor of at least one deviceincluding at least one endpoint.

Example 86 includes the subject matter of Example 85 and optionally,wherein the device descriptor indicates one or more characteristics ofthe device including the endpoint.

Example 87 includes the subject matter of Example 85 or 86 andoptionally, wherein the instructions result in communicating at leastone control transfer request from the first device to the second device,the control transfer request to request the second device to transfer tothe first device control information including a device descriptor ofthe device including the endpoint; and communicating at least onecontrol transfer response from the second device to the first device,the control transfer response including the control information.

Example 88 includes the subject matter of any one of Examples 85-87 andoptionally, wherein the instructions result in communicating at leastone update device request from the first device to the second device,the update device request including the device descriptor.

Example 89 includes the subject matter of any one of Examples 85-88 andoptionally, wherein the instructions result in communicating between thefirst and second devices at least one message including at least oneendpoint descriptor corresponding to the at least one endpoint, theendpoint descriptor including a credit consumption unit (CCU) definedwith respect to the endpoint.

Example 90 includes the subject matter of Example 89 and optionally,wherein the CCU is based on the device descriptor.

Example 91 includes the subject matter of any one of Examples 85-90 andoptionally, wherein the first device comprises a host Universal SerialBus (USB) Protocol Adaptation Layer (PAL), and wherein the second devicecomprises a Device USB PAL.

Example 92 includes the subject matter of any one of Examples 85-91 andoptionally, wherein the communication link comprises a wirelesscommunication link.

Example 93 includes the subject matter of Example 92 and optionally,wherein the wireless communication link comprises a wireless gigabit(WiGig) link.

Example 94 includes the subject matter of any one of Examples 85-93 andoptionally, wherein the first device comprises a WiGig Serial Extension(WSE) host, and wherein the second device comprises a WSE Device.

Example 95 includes an apparatus of communication, the apparatuscomprising means for controlling the transfer of a stream of data from afirst device to a second device over a communication link, the stream ofdata including data to be delivered to a plurality of endpoints, thecontrolling including communicating between the first and second devicesat least one message including at least one endpoint-specific creditconsumption unit (CCU) defined with respect to at least one endpoint ofthe plurality of endpoints.

Example 96 includes the subject matter of Example 95 and optionally,wherein the message includes two or more endpoint descriptorscorresponding to two or more endpoints of the plurality of endpoints,and wherein the two or more endpoint descriptors include two or moredifferent CCUs defined with respect to the two or more endpoints.

Example 97 includes the subject matter of Example 95 or 96 andoptionally, wherein the CCU defines a unit by which the first device isto keep track of buffer space available on the second device forbuffering data for the endpoint.

Example 98 includes the subject matter of any one of Examples 95-97 andoptionally, comprising means for receiving the message, and accountingfor consumed credits for the endpoint in multiples of the CCU,regardless of an amount of data to be transferred from the first deviceto the endpoint.

Example 99 includes the subject matter of any one of Examples 95-98 andoptionally, comprising means for transmitting the message, andtransmitting a message including granted credit, which is allocated withrespect to the endpoint, the granted credit is represented as a multipleof the CCU.

Example 100 includes the subject matter of any one of Examples 95-99 andoptionally, comprising means for communicating between the second andfirst devices a message including granted credit, which is allocatedwith respect to the endpoint, wherein the granted credit is representedas a multiple of the CCU.

Example 101 includes the subject matter of any one of Examples 95-100and optionally, wherein the message includes an endpoint handleresponse.

Example 102 includes the subject matter of Example 101 and optionally,comprising means for communicating at least one endpoint handle requestfrom the first device to the second device, the endpoint handle requestincluding an endpoint descriptor of the endpoint, and wherein theendpoint handle response includes the CCU of the endpoint.

Example 103 includes the subject matter of any one of Examples 95-101and optionally, comprising means for communicating an update devicerequest from the first device to the second device, the update devicerequest including a device descriptor of a Universal-Serial-Bus (USB)device including the endpoint.

Example 104 includes the subject matter of Example 103 and optionally,comprising means for defining the CCU based on the device descriptor.

Example 105 includes the subject matter of any one of Examples 95-104and optionally, comprising means for communicating a control transferrequest from the first device to the second device, the control transferrequest requesting the second device to transfer to the first devicecontrol information including a device descriptor of a device includingone or more of the plurality of endpoints; means for communicating acontrol transfer response from the second device to the first device,the control transfer response including the control information; andmeans for communicating an update device request from the first deviceto the second device, the update device request including the devicedescriptor.

Example 106 includes the subject matter of any one of Examples 95-105and optionally, wherein the first device comprises a host UniversalSerial Bus (USB) Protocol Adaptation Layer (PAL), and wherein the seconddevice comprises a Device USB PAL.

Example 107 includes the subject matter of any one of Examples 95-106and optionally, wherein the communication link comprises a wirelesscommunication link.

Example 108 includes the subject matter of Example 107 and optionally,wherein the wireless communication link comprises a wireless gigabit(WiGig) link.

Example 109 includes the subject matter of any one of Examples 95-108and optionally, wherein the first device comprises a WiGig SerialExtension (WSE) host, and wherein the second device comprises a WSEDevice.

Example 110 includes an apparatus of communication, the apparatuscomprising means for controlling the transfer of a stream of data from afirst device to a second device over a communication network, the streamof data including data to be delivered to a plurality of endpoints, thecontrolling including communicating from the first device to the seconddevice a message including a device descriptor of at least one deviceincluding at least one endpoint.

Example 111 includes the subject matter of Example 110 and optionally,wherein the device descriptor indicates one or more characteristics ofthe device including the endpoint.

Example 112 includes the subject matter of Example 110 or 111 andoptionally, comprising means for communicating at least one controltransfer request from the first device to the second device, the controltransfer request to request the second device to transfer to the firstdevice control information including a device descriptor of the deviceincluding the endpoint; and means for communicating at least one controltransfer response from the second device to the first device, thecontrol transfer response including the control information.

Example 113 includes the subject matter of any one of Examples 110-112and optionally, comprising means for communicating at least one updatedevice request from the first device to the second device, the updatedevice request including the device descriptor.

Example 114 includes the subject matter of any one of Examples 110-113and optionally, comprising means for communicating between the first andsecond devices at least one message including at least one endpointdescriptor corresponding to the at least one endpoint, the endpointdescriptor including a credit consumption unit (CCU) defined withrespect to the endpoint.

Example 115 includes the subject matter of Example 114 and optionally,wherein the CCU is based on the device descriptor.

Example 116 includes the subject matter of any one of Examples 110-115and optionally, wherein the first device comprises a host UniversalSerial Bus (USB) Protocol Adaptation Layer (PAL), and wherein the seconddevice comprises a Device USB PAL.

Example 117 includes the subject matter of any one of Examples 110-116and optionally, wherein the communication link comprises a wirelesscommunication link.

Example 118 includes the subject matter of Example 117 and optionally,wherein the wireless communication link comprises a wireless gigabit(WiGig) link.

Example 119 includes the subject matter of any one of Examples 110-118and optionally, wherein the first device comprises a WiGig SerialExtension (WSE) host, and wherein the second device comprises a WSEDevice.

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features have been illustrated and described herein, manyvariations, modifications, substitutions, changes, additions,improvements and equivalents may occur to those skilled in the art. Itis, therefore, to be understood that the appended claims are intended tocover all such modifications and changes as fall within the true spiritof the invention.

What is claimed is:
 1. An apparatus comprising: a communication unit tocommunicate data between a first device and a second device over acommunication link, said data including data to be delivered from saidfirst device to a plurality of endpoints via said second device, whereinsaid communication unit is to communicate between the first and seconddevices at least one first message including at least one endpointdescriptor corresponding to at least one endpoint of said plurality ofendpoints, said endpoint descriptor including a credit consumption unit(CCU) defined with respect to said endpoint, said communication unit isconfigured to communicate between said second and first devices a secondmessage comprising granted credit, which is allocated with respect tosaid endpoint, said granted credit is represented as a multiple of saidCCU, and wherein said communication unit is configured to communicate acontrol transfer request from the first device to the second device, thecontrol transfer request to request the second device to transfer to thefirst device control information comprising a device descriptor of adevice including one or more of said plurality of endpoints, saidcommunication unit is configured to communicate a control transferresponse from said second device to said first device, the controltransfer response comprising the control information, said communicationunit is configured to communicate an update device request from thefirst device to the second device, the update device request comprisingsaid device descriptor.
 2. The apparatus of claim 1, wherein said firstmessage includes two or more endpoint descriptors corresponding to twoor more endpoints of said plurality of endpoints, and wherein said twoor more endpoint descriptors include two or more different CCUs withrespect to said two or more endpoints.
 3. The apparatus of claim 1,wherein the CCU indicates a unit by which the first device is to keeptrack of buffer space available on said second device for buffering datafor said endpoint.
 4. The apparatus of claim 1, wherein saidcommunication unit is to receive said first message and to account forconsumed credits for said endpoint in multiples of the CCU, regardlessof an amount of data to be transferred from the first device to theendpoint.
 5. The apparatus of claim 1, wherein said communication unitis to transmit said first message and to transmit the second messageincluding the granted credit, which is allocated with respect to saidendpoint.
 6. The apparatus of claim 1, wherein said first messageincludes an endpoint handle response.
 7. The apparatus of claim 6,wherein said communication unit is to communicate at least one endpointhandle request from the first device to the second device, the endpointhandle request including the endpoint descriptor of said endpoint, andwherein said endpoint handle response includes the CCU of said endpoint.8. The apparatus of claim 1, wherein said communication unit is tocommunicate an update device request from the first device to the seconddevice, the update device request including a device descriptor of aUniversal-Serial-Bus (USB) device including said endpoint.
 9. Theapparatus of claim 8, wherein said communication unit is to determinesaid CCU based on said device descriptor.
 10. The apparatus of claim 1,wherein said first device comprises a host Universal Serial Bus (USB)Protocol Adaptation Layer (PAL), and wherein said second devicecomprises a Device USB PAL.
 11. The apparatus of claim 1, wherein saidcommunication link comprises a wireless communication link, theapparatus comprising an antenna to communicate over said wirelesscommunication link.
 12. The apparatus of claim 11, wherein said wirelesscommunication link comprises a wireless gigabit (WiGig) link.
 13. Theapparatus of claim 1, wherein said first device comprises a WiGig SerialExtension (WSE) host, and wherein said second device comprises a WSEDevice.
 14. A system comprising: a device comprising: a networkinterface to communicate over a network; and a wireless gigabit (WiGig)Serial Extension (WSE) controller to perform the functionality of a WSEhost or a WSE device to communicate Universal Serial Bus (USB) databetween a USB host and a USB device over said network, said dataincluding data to be delivered from said USB host to a plurality ofendpoints of said USB device, wherein said WSE controller is configuredto communicate from the WSE host to the WSE device a message including adevice descriptor of said USB device, the device descriptor to indicateone or more characteristics of said USB device, said WSE controller isconfigured to communicate at least one control transfer request from theWSE host to the WSE device, the control transfer request to request theWSE device to transfer to the WSE host control information comprisingthe device descriptor of the USB device, said WSE controller isconfigured to communicate at least one control transfer response fromsaid WSE device to said WSE host, the control transfer responsecomprising the control information.
 15. The system of claim 14, whereinsaid WSE controller is to communicate at least one update device requestfrom the WSE host to the WSE device, the update device request includingsaid device descriptor.
 16. The system of claim 14, wherein said WSEcontroller is to communicate between the WSE host and WSE device atleast one message including at least one endpoint descriptorcorresponding to at least one endpoint, said endpoint descriptorincluding a credit consumption unit (CCU) defined with respect to saidendpoint.
 17. The system of claim 16, wherein said CCU is based on saiddevice descriptor.
 18. A method comprising: controlling the transfer ofa stream of data from a first device to a second device over acommunication link, the stream of data including data to be delivered toa plurality of endpoints, the controlling including: communicating acontrol transfer request from the first device to the second device, thecontrol transfer request to request the second device to transfer to thefirst device control information comprising a device descriptor of adevice including one or more of said plurality of endpoints;communicating a control transfer response from said second device tosaid first device, the control transfer response comprising the controlinformation; communicating an update device request from the firstdevice to the second device, the update device request comprising saiddevice descriptor; communicating between the first and second devices atleast one first message including at least one credit consumption unit(CCU) defined with respect to at least one endpoint of said plurality ofendpoints; and communicating between said second and first devices asecond message comprising granted credit, which is allocated withrespect to said endpoint, said granted credit is represented as amultiple of said CCU.
 19. The method of claim 18, wherein said firstmessage includes two or more endpoint descriptors corresponding to twoor more endpoints of said plurality of endpoints, and wherein said twoor more endpoint descriptors include two or more different CCUs definedwith respect to said two or more endpoints.
 20. The method of claim 18,wherein the update device request comprises a device descriptor of aUniversal-Serial-Bus (USB) device including said endpoint.
 21. Themethod of claim 18 comprising determining said CCU based on said devicedescriptor.
 22. A product including a non-transitory storage mediumhaving stored thereon instructions that, when executed by a machine,result in: controlling the transfer of a stream of data from a firstdevice to a second device over a communication link, the stream of dataincluding data to be delivered to a plurality of endpoints, thecontrolling including communicating between the first and second devicesat least one first message including at least one credit consumptionunit (CCU) defined with respect to at least one endpoint of saidplurality of endpoints, and communicating between said second and firstdevices a second message comprising granted credit, which is allocatedwith respect to said endpoint, said granted credit is represented as amultiple of said CCU, wherein the instructions result in communicating acontrol transfer request from the first device to the second device, thecontrol transfer request to request the second device to transfer to thefirst device control information including a device descriptor of adevice including one or more of said plurality of endpoints;communicating a control transfer response from said second device tosaid first device, the control transfer response including the controlinformation; and communicating an update device request from the firstdevice to the second device, the update device request including saiddevice descriptor.
 23. The product of claim 22, wherein said firstmessage includes two or more endpoint descriptors corresponding to twoor more endpoints of said plurality of endpoints, and wherein said twoor more endpoint descriptors include two or more different CCUs definedwith respect to said two or more endpoints.
 24. The product of claim 22,wherein the update device request comprises a device descriptor of aUniversal-Serial-Bus (USB) device including said endpoint.
 25. Theproduct of claim 24, wherein the instructions result in determining saidCCU based on said device descriptor.